fix: use create-pull-request action for leaderboard updates - #642
Conversation
|
@ramnnn2006 is attempting to deploy a commit to the Prashantkumar Khatri's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Hi @ramnnn2006, Thanks for opening this pull request. This PR has been automatically classified based on the files modified. Applied Labels
Primary Review Area
Reviewer@ShantKhatri has been identified as the primary reviewer for this pull request. If you have any questions regarding the affected area or implementation details, feel free to reach out to the assigned reviewer. Thank you for your contribution! |
CI — All Checks PassedBackend — SKIP
Mobile — SKIP
Web — SKIP
Last updated: |
|
Congratulations @ramnnn2006 on getting PR #642 merged! Thank you for your contribution to the project. To receive the appropriate GSSoC labels and recognition, please mention @Harxhit in the #get-labels channel on our Discord server and share your merged PR link. |
Summary
The contributor leaderboard workflow currently fails because it tries to push updates directly to the main branch, which is protected. This pull request modifies the workflow to use the
peter-evans/create-pull-requestaction. Instead of pushing to main, the workflow will now open an automated pull request with the updated leaderboard data.Closes #641
Type of Change
What Changed
pull-requestspermission in.github/workflows/leaderboard.ymlfromreadtowriteto allow the action to open pull requests..github/workflows/leaderboard.ymlwith thepeter-evans/create-pull-requestaction.How to Test
leaderboard.jsonfile, and open a pull request without any push block errors.Checklist
npm run lintpasses).npm run typecheck --workspaces --if-present).npm run test --workspaces --if-present).console.logor debug statements left in the code.